Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create blog Inside the Pharmaverse #131

Merged
merged 6 commits into from
Mar 5, 2024
Merged

Conversation

MichaelRimler
Copy link
Collaborator

Blog from Pharmaverse Council on 'Inside the Pharmaverse'

@rossfarrugia rossfarrugia linked an issue Mar 4, 2024 that may be closed by this pull request
R/create_blogpost.R Outdated Show resolved Hide resolved
@rossfarrugia
Copy link
Contributor

Link checks fail here for another blog and I see spelling CI fails too so Ben and Edoardo might advise we need to fix here.

Comment on lines 32 to 33
These individuals included Ross Farrugia (Roche), Sumesh Kalappurakal (Johnson & Johnson), Michael Rimler (GSK), and Mike Stackhouse (Atorus).
Each had historical experience with R adoption, through their primary roles within their respective organizations.
Copy link
Collaborator

@bms63 bms63 Mar 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pooja's ISCR post cross-links to linkedin - maybe can do same here for those willing? I think folks reading this post would be interested in following you four!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll add in those that I have.

Comment on lines +59 to +62
## Pharmaverse Objective

Pharmaverse aims to promote the collaborative development of curated open-source R packages for clinical reporting in pharma.
Indirectly, we also strive to encourage and increase R adoption within the industry and facilitate communication and collaboration among both R users and R developers.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we lead with this section?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good thought - I think it is okay as is.

The [Pharmaverse website](https://pharmaverse.org/) states that “\[a\]nyone is free to choose any selection of Pharmaverse recommended software or those from any other source.” In addition, Pharmaverse does not seek to engage or get endorsement from any health authority.
We are merely trying to provide a public service to help individuals and organizations involved in clinical reporting navigate a vast field of available R packages licensed as open source.

## So, what really is Pharmaverse?
Copy link
Collaborator

@bms63 bms63 Mar 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about the example site and showing how we take pharmaverse and other
packages to build our common deliverables (ADaMs, TLFs. xpts, etc)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will add a simp;le sentence to connect the reader

Copy link
Collaborator

@bms63 bms63 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really nice!! Just a few minor comments. No issues if not implemented. I have approved.

@bms63
Copy link
Collaborator

bms63 commented Mar 4, 2024

I fixed spelling issue as well.

@MichaelRimler
Copy link
Collaborator Author

Link checks fail here for another blog and I see spelling CI fails too so Ben and Edoardo might advise we need to fix here.

I checked the spelling flags and all are acceptable to me (intentional). I hope the same for @manciniedoardo and @bms63

@MichaelRimler
Copy link
Collaborator Author

Comments updated and pushed.

@bms63
Copy link
Collaborator

bms63 commented Mar 4, 2024

@rossfarrugia im good with this. feel free to merge in once you are happy - the website takes about 5-10 minutes to rebuild itself

do you all mind doing a post on slack/linked in once published? I will repost on linked in

Copy link
Collaborator

@manciniedoardo manciniedoardo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, a couple of comments from me but nothing major so feel free to implement or ignore. Thanks for writing a blog post!


Greetings, Pharmaverse phriends!

Now that the {pharmaverse} has been around for a few years and seems to be making an impact on clinical reporting (yay!), we wanted to take an opportunity to cast a light on some of the inner workings of Pharmaverse and its Council (us).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Throughout the post, both {Pharmaverse} and Pharmaverse are used - suggest sticking to one?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used {Pharmaverse} once, intentionally, for style. Unless you see other instances, I think it's ok.


Pharmaverse is essentially two things:

1. Pharmaverse is a list of packages curated by the Pharmaverse Council and Working Groups, primarily communicated via the Pharmaverse website.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Pharmaverse is a list of packages curated by the Pharmaverse Council and Working Groups, primarily communicated via the Pharmaverse website.
1. A list of packages curated by the Pharmaverse Council and Working Groups, primarily communicated via the Pharmaverse website.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The grammar may be poor, but I like the way it reads by reiterating 'Pharmaverse'

1. Pharmaverse is a list of packages curated by the Pharmaverse Council and Working Groups, primarily communicated via the Pharmaverse website.
Pharmaverse also maintains an [R-universe build](https://pharmaverse.r-universe.dev/builds) for ease of use outside GxP settings.

2. Pharmaverse is a community of R users and R developers “working to promote collaborative development of curated open-source R packages for clinical reporting usage in pharma.”
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Pharmaverse is a community of R users and R developers “working to promote collaborative development of curated open-source R packages for clinical reporting usage in pharma.”
2. A community of R users and R developers “working to promote collaborative development of curated open-source R packages for clinical reporting usage in pharma.”

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also where does this quote come from? Might be beneficial to link a source?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@manciniedoardo same comment as above.

Quote comes from https://pharmaverse.org/
image

@MichaelRimler MichaelRimler merged commit e542bdb into main Mar 5, 2024
4 checks passed
@MichaelRimler MichaelRimler deleted the 130_InsidePharmaverse branch March 5, 2024 10:59
@rossfarrugia
Copy link
Contributor

do you all mind doing a post on slack/linked in once published? I will repost on linked in

Will leave this to @MichaelRimler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blog Post: Inside Pharmaverse
6 participants